Long-term evolution (LTE) policy control and charging rules function (PCRF) selection

ABSTRACT

The PCRF Selection Function selects the PCRF for an IP-CAN session. In embodiments, the PCRF Selection Function is located in the HSS and/or the 3GPP AAA server. The PCRF Selection Function is only required to be located in the HSS if a Bearer Binding and Event Reporting Function (BBERF) is deployed in the serving gateway. In this case, the PCRF selection takes place at the time that the PDN Gateway is selected and returned by the HSS to the serving gateway over the HSS to MME interface (S6a).

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional PatentApplication No. 61/059,245, entitled “Long-Term Evolution (LTE) PolicyControl and Charging Rules Function (PCRF) Selection”, filed on Jun. 5,2008, which is hereby expressly incorporated by reference in itsentirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to Third Generation PartnershipProject (3GPP networks) and specifically to packet policy control andcharging rules function selection in a 3GPP network.

2. Background Art

An increasingly large number of individuals use portable computingdevices, such as laptop computers, personal data assistants (PDAs),smart phones and the like, to support mobile communications. The numberof computing devices, and the number of networks that these devicesconnect to, has increased dramatically in recent years. Similarly, anincreasing number of wireless Internet access services have beenappearing in airports, cafes and book stores.

As telecommunications technology continues to evolve to meet this everincreasing demand, service providers continue to make investments instate-of-the-art technology in order to remain at the forefront ofofferings in the marketplace. However, in order to maximize their returnon investment, service providers are constantly challenged to moreeffectively market their technology offerings by offering richer choicesto their subscriber base, and to deliver those choices in a timely andseamless fashion.

The Third Generation Partnership Project (3GPP) long term evolution(LTE) reference architecture defines the use of one or more policycontrol and charging rules functions (PCRF). As the name implies, PCRFprovides policy control decision and flow-based charging controlfunctionalities. For example, the PCRF provides network controlregarding service data flow detection, gating, quality of service (QoS),and flow based charging to the policy control enforcement function. Inaddition, the PCRF may also apply security procedures before acceptingservice information from an Application Function (AF). Additionally, thePCRF determines how a certain data flow is treated in the policy controlenforcement function and ensures that the enforcement function trafficmapping and treatment is in accordance with the user's subscriptionprofile. For example, the PCRF delivers rules around trafficclassification, QoS, and charging to the enforcement functions.

The Diameter Routing Agent (DRA) maintains information about useridentity, access point name (APN), the user equipment IP address(es) andthe selected PCRF for an IP-connectivity access network (IP-CAN)session. The DRA initially allocates a PCRF for a session. Additionally,the DRA may be queried by other network entities that need to change anexisting session or establish a new Quality of Service (QoS). The DRAreturns the address of the PCRF to the requesting entity.

When the DRA first receives a request for an IP-CAN session, the DRAselects a suitable PCRF for the IP-CAN session and stores the PCRFaddress. Subsequently, the DRA can retrieve the selected PCRF addressaccording to information carried by the incoming requests from otherentities.

Three methods are currently being proposed for accessing a PCRF for anexisting session. A redirect DRA is an enhanced form of the Diameterredirect agent functionality. The redirect DRA is used to redirectclients to the appropriate PCRF. A proxy DRA is an enhanced form of theDiameter proxy agent functionality. A proxy DRA is used to forwardmessages from clients to the appropriate PCRF. Finally, the optimizedproxy DRA is a hybrid solution where a proxy is used on IP-CAN sessionestablishment and termination but session modification messages are sentdirectly to the selected PCRF.

All of these solutions require deployment of additional DRA elements inthe network. Furthermore, the DRA messaging introduces additionallatency on IP CAN session establishment and termination. The redirectDRA and optimized proxy DRA solutions also have transport connectionscaling issues and the proxy DRA solution introduces additional latencyto IP CAN session modification exchanges due to the message forwarding.

What is therefore needed is a technique for accessing a PCRF for anexisting session that does not introduce additional latency nor posetransport connection scaling issues.

BRIEF SUMMARY OF THE INVENTION

In an embodiment of the present invention, the DRA is considered as aPCRF Selection Function, within an existing element, rather than as anew element. The PCRF Selection Function shares a common state storethat contains the User-Equipment-to-PCRF binding for a given IP-Cansession.

In various embodiments of the present invention, the PCRF SelectionFunction can be housed in either the HSS and/or the 3GPP AAA server. Noadditional interfaces or changes to existing interfaces are required foreither 3GPP access or non-3GPP access.

In a further embodiment of the present invention, the PCRF SelectionFunction is required to be located in the HSS only if a Bearer Bindingand Event Reporting Function (BBERF) is deployed in the serving gateway.In this embodiment, the PCRF selection takes place at the same time thatthe PDN Gateway is selected and returned by the HSS to the ServingGateway over the S6a interface.

In other embodiments of the present invention, the selected PCRF mayalso be communicated to the PDN Gateway over the S8 interface, if it isalready known by the serving gateway.

In a still further embodiment of the present invention, the PCRF mayalso be communicated over the S6b interface (interface between the 3GPPAAA and the PDN gateway) if a 3GPP AAA is deployed, or over an SGiinterface if a AAA function is deployed to facilitate the operator's IPservices. For IMS and non-IMS application functions, the selected PCRFcan be returned by the HSS to the application over the Sh interface.Because each of the embodiments uses existing signaling connections, thetransport connection scaling issues present with the re-direct DRA donot exist with the HSS-based PCRF Selection Function and/or the 3GPPAAA-based PCRF Selection Function. Moreover, no additional latency inthe IP-CAN session establishment, modification, or termination results.

Further embodiments, features, and advantages of the invention, as wellas the structure and operation of the various embodiments of theinvention are described in detail below with reference to accompanyingdrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form a partof the specification, illustrate the present invention and, togetherwith the description, further serve to explain the principles of theinvention and to enable a person skilled in the pertinent art to makeand use the invention.

FIG. 1 depicts a conventional Third Generation Partnership Project(3GPP) long term evolution (LTE) reference architecture.

FIG. 2 depicts a block diagram of an operating environment for HSS-basedand/or 3GPP AAA-based PCRF Selection Function, according to embodimentsof the present invention.

FIG. 3 depicts a flowchart of an exemplary method for HSS-based and/or3GPP AAA-based PCRF Selection Function, according to embodiments of thepresent invention.

FIG. 4 is a diagram of a computer system on which the methods andsystems herein described can be implemented, according to an embodimentof the invention.

The present invention will now be described with reference to theaccompanying drawings. In the drawings, like reference numbers canindicate identical or functionally similar elements. Additionally, theleft-most digit(s) of a reference number may identify the drawing inwhich the reference number first appears.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 depicts a conventional Third Generation Partnership Project(3GPP) long term evolution (LTE) reference architecture 100. Referencearchitecture 100 includes a 3GPP network 102 and one or more non-3GPPnetworks 104. 3GPP network 102 includes 3GPP access 110, one or morepacket data network (PDN) gateways 120, one or more policy control andcharging rules function (PCRF) 140 a-n, a Diameter routing agent (DRA)150, a home subscriber server (HSS) 160, and a 3GPP authentication,authorization, and accounting (AAA) server 170.

3GPP access 110 represents a collection of functional entities andinterfaces that provide access for user equipment to 3GPP network 102.3GPP access 110 includes a mobility management entity (MME) and anevolved universal terrestrial radio access node (E-UTRAN). Userequipment (UE1) 106 a accesses 3GPP network 102 via the 3GPP access“cloud” 110.

The MME manages mobility for user equipment. No user data packets gothrough the MME. The MME is configured to perform authentication andauthorization functions, non-access stratum (NAS) signaling, securitynegotiations, serving gateway and/or PDN gateway selection, and UEreachability.

The MME may further be co-located with serving gateway 115. TheMME/serving gateway acts as a foreign agent for a mobile IP session.Serving gateway 115 forwards and receives packets to and from the nodewhere the user equipment is being served.

PDN-GW 120 interfaces with external packet networks (e.g., theInternet). The PDN-GW provides an anchor for 3GPP and non-3GPP mobile IPsessions. That is, the PDN-GW acts as the home agent for the mobile IPsession.

In the LTE architecture, two tunneling protocols are defined forenabling mobility, Proxy Mobile IP (PMIP) and GPRS Tunneling Protocol(GTP). Both protocols require a PDN-GW acting as an IP anchor point formobility. The protocols from Serving Gateway to PDN-GW are referred toas “PMIP-based S8” and “GTP-based S8.” GTP is not supported in anon-3GPP access network. In embodiments, a PDN-GW 120 supports both GTPand PMIP on the same node.

The PDN-GW 120 may also include a policy and charging enforcementfunction (PCEF). The PCEF provides service data flow detection, userplane traffic handling, triggering control plane session management,Quality of Service (QoS) handling, service data flow measurement, aswell as online and offline charging interactions. The PCEF enforces thepolicy control as indicated by the policy control and charging rulesfunction (PCRF) 140.

PCRF 140 provides policy control decision and flow based chargingcontrol functionalities. For example, the PCRF provides network controlregarding service data flow detection, gating, Quality of Service (QoS),and flow based charging to the policy control enforcement function. APCRF may also apply security procedures before accepting serviceinformation from an Application Function (AF). Additionally, the PCRFdetermines how a certain data flow is treated in the policy controlenforcement function and ensures that the enforcement function trafficmapping and treatment is in accordance with the user's subscriptionprofile. For example, PCRF 140 delivers rules around trafficclassification, QoS, and charging to the enforcement functions (e.g., inthe PDN gateway via the Gx interface or in the serving gateway 115 viathe Gxc interface). The PCRFs in a 3GPP network belong to one or moreDiameter realms.

3GPP network 102 also includes the operator's IP services 180.Operator's IP services 180 includes one or more application functions(AFs) offered by an operator. AFs communicate with a PCRF via the Rxinterface. An exemplary AF that may be offered by an operator is IPMultimedia Subsystem (IMS). IMS delivers IP multimedia services tomobile users. One function of IMS is the Call Session Control Function(CSCF). The CSCF may influence the QoS, bandwidth, or other attributesof an established IP-CAN session.

Diameter Routing Agent (DRA) 150 maintains information about useridentity, access point name (APN), the user equipment IP address(es) andthe selected PCRF for an IP-CAN session. DRA 150 initially allocates aPCRF for a session. Additionally, DRA may be queried by other networkentities that need to change an existing session or establish a newQuality of Service (QoS). The DRA returns the address of the PCRF to therequesting entity.

When DRA 150 first receives a request for an IP-CAN session (e.g, fromPDN gateway 120), the DRA selects a suitable PCRF for the IP-CAN sessionand stores the PCRF address. Subsequently, DRA 150 can retrieve theselected PCRF address according to information carried by the incomingrequests from other entities (e.g., an AF). Three methods are currentlybeing proposed for accessing a PCRF for an existing session.

A redirect DRA is an enhanced form of the Diameter redirect agentfunctionality. The redirect DRA is used to redirect clients (e.g., IMSfunction) to the appropriate PCRF. A proxy DRA is an enhanced form ofthe Diameter proxy agent functionality. A proxy DRA is used to forwardmessages from clients to the appropriate PCRF. Finally, the optimizedproxy DRA is a hybrid solution where a proxy is used on IP-CAN sessionestablishment and termination but session modification messages are sentdirectly to the selected PCRF.

All of these solutions require deployment of additional DRA elements inthe network. Furthermore, the DRA messaging introduces additionallatency on IP-CAN session establishment and termination. The redirectDRA and optimized proxy DRA solutions also have transport connectionscaling issues and the proxy DRA solution introduces additional latencyto IP CAN session modification exchanges due to the message forwarding.

HSS 160 stores a record for each subscriber to 3GPP network 105. Thesubscriber record includes a subscription profile, authenticationvectors, and a list of allowed Access Point Names (APNs) for eachsubscriber. Each APN has a list of allowed PDN-GWs for the subscriber.An APN may be considered as the network name (e.g., Internet, corporateintranet, etc.).

User equipment 1 (UE1) 106 a attaches to 3GPP network 102 over the 3GPPRadio Access Network (RAN). Upon receiving the connection attempt, UE1106 a is then authenticated/authorized by an MME. The MME also invokesgateway selection function to select a PDN gateway for the IP-CANsession with UE1 106 a. Gateway selection function 140 accesses HSS 150to retrieve a list of PDN-GWs serving the identified APN. The HSS mayalso return the subscriber profile and authentication vectors for UE1.

User equipment 2 (UE2) 106 b attempts to access 3GPP network 102 via anon-3GPP network access mechanism. The network access may be trusted(e.g., trusted non-3GPP IP access 194) or untrusted (untrusted non-3GPPaccess 192). Untrusted IP access 192 accesses 3GPP network elements viaan evolved Packet Data Gateway (ePDG). For example, access from anon-3GPP network may be via a Wi-Fi network or a non-GSM wirelessnetwork such as CDMA.

In the non-3GPP access scenario, an equivalent to the serving gatewayoriginates an authentication request. The authentication request may besent to the 3GPP AAA proxy sitting on the border of the network. The3GPP AAA proxy accesses the HSS via the 3GPP AAA to retrieve theauthentication vectors, subscriber profiles, and a list of allowedPDN-GWs.

Embodiments of the invention consider the DRA as a function rather thana new element. These embodiments locate the DRA function in the HSSand/or in the 3GPP AAA server. The DRA function in these elements sharesa common state store that contains the UE-to-PCRF binding for a givenIP-CAN session.

FIG. 2 depicts a block diagram of an operating environment 200 forHSS-based and/or 3GPP AAA-based PCRF selection, according to embodimentsof the present invention. In this embodiment, a PCRF Selection Functionis located in the HSS and/or the 3GPP AAA. No additional interfaces orchanges to existing interfaces are required for either 3GPP access ornon-3GPP access.

Operating environment 200 includes a 3GPP network 202 and one or morenon-3GPP networks 204. 3GPP network 202 includes 3GPP access 210, one ormore PDN gateways 220, one or more PCRFs 240, an HSS 260, and a 3GPP AAAserver 270.

In an embodiment, HSS 260 includes a PCRF Selection Function 250. In anembodiment, 3GPP AAA server 270 may also include a PCRF SelectionFunction 250.

Mandatory exchanges have been defined for various network entities(e.g., PDN gateway IMS CSCF). These exchanges can be enhanced to includethe delivery of PCRF information, when required. For example, during atraditional attach procedure, the HSS is accessed to obtain certain data(e.g., authentication vectors) required to establish a session. As partof the existing exchange, the reply from the HSS (over the S6ainterface) is modified to include the assigned PCRF.

For IMS, the CSCF is required to perform authentication andauthorization (e.g., authorizing an IMS or video call). As part of theexisting exchange between the CSCF and IMS, the assigned PCRF isreturned over the Sh interface.

In an embodiment, the PCRF Selection Function is only required to belocated in the HSS if a Bearer Binding and Event Reporting Function(BBERF) is deployed in the serving gateway. In this case, the PCRFselection takes place at the same time that the PDN Gateway is selectedand returned by the HSS to the Serving Gateway over the S6a interface.

In addition to exchanges during session establishment, many additionalexchanges occur after a session has been established. For example, aspart of the exchanges in IMS, a message is sent to the HSS to determinewhether the subscriber is valid and allowed to initiate a voice call. Aspart of that exchange, the PCRF Selection Function in the HSS isaccessed to retrieve the PCRF. The PCRF is then returned, along with theother elements of the exchange, over the Sh interface.

The selected PCRF may also be communicated to PDN Gateway 220 over theS8 interface, if it is already known by the serving gateway. The S8interface is the interface between a PDN gateway in the home network anda serving gateway in a visited network. The PCRF may also becommunicated over the S6b interface (interface between the 3GPP AAA andthe PDN gateway) if a 3GPP AAA is deployed, or over an SGi interface ifan AAA function is deployed to facilitate the operator's IP services.For IMS and non-IMS application functions, the selected PCRF can bereturned by the HSS to the application over the Sh interface.

FIG. 3 depicts a flowchart 300 of an exemplary method for the PCRFselection, according to embodiments of the present invention. FIG. 3 isdescribed with continued reference to the operating environment of FIG.2. However, method 300 is not limited to that embodiment. Method 300begins at step 310.

In step 320, a request for PCRF information is received by a PCRFSelection Function module housed in a non-DRA element, e.g. in aHSS-based PCRF Selection Function and/or 3GPP AAA-based PCRF SelectionFunction.

In step 330, the DRA module delivers the requested PCRF information viaa standard 3GPP interface.

Method 300 ends at step 340.

Because embodiments use existing signaling connections, the transportconnection scaling issues present with the redirect DRA do not existwith the HSS-based PCRF Selection Function and/or 3GPP AAA-based PCRFSelection Function. As the selected PCRF information is included inexisting message exchanges, no additional latency in IP-CAN sessionestablishment, modification, or termination exists.

However, the embodiments share one of the characteristics of theredirect DRA solution in that the function allocating the PCRF has noknowledge of a PCRF failure or a network failure resulting in the PCRFbeing unreachable from the gateway or AF. The feedback on PCRF failureor unreachability can be provided over the existing transportconnections to the PCRF Selection Function in the HSS or 3GPP AAA.However, it will require new message exchanges. These additional messageexchanges are only used in failure cases so the additional load on thePCRF clients is negligible.

Computer System Implementation

Computer 400 includes one or more processors (also called centralprocessing units, or CPUs), such as processor 410. Processor 410 isconnected to communication bus 420. Computer 400 also includes a main orprimary memory 430, preferably random access memory (RAM). Primarymemory 430 has stored therein control logic (computer software), anddata.

Computer 400 may also include one or more secondary storage devices 440.Secondary storage devices 440 include, for example, hard disk drive 450and/or removable storage device or drive 460. Removable storage drive460 represents a floppy disk drive, a magnetic tape drive, a compactdisk drive, an optical storage device, tape backup, ZIP drive, JAZZdrive, etc.

Removable storage drive 460 interacts with removable storage unit 470.As will be appreciated, removable storage unit 460 includes a computerusable or readable storage medium having stored therein computersoftware (control logic) and/or data. Removable storage drive 460 readsfrom and/or writes to the removable storage unit 470 in a well knownmanner.

Removable storage unit 470, also called a program storage device or acomputer program product, represents a floppy disk, magnetic tape,compact disk, optical storage disk, ZIP disk, JAZZ disk/tape, or anyother computer data storage device. Program storage devices or computerprogram products also include any device in which computer programs canbe stored, such as hard drives, ROM or memory cards, etc.

In an embodiment, the present invention is directed to computer programproducts or program storage devices having software that enablescomputer 400, or multiple computer 400 s to perform any combination ofthe functions described herein

Computer programs (also called computer control logic) are stored inmain memory 430 and/or the secondary storage devices 440. Such computerprograms, when executed, direct computer 400 to perform the functions ofthe present invention as discussed herein. In particular, the computerprograms, when executed, enable processor 410 to perform the functionsof the present invention. Accordingly, such computer programs representcontrollers of the computer 400.

Computer 400 also includes input/output/display devices 480, such asmonitors, keyboards, pointing devices, etc.

Computer 400 further includes a communication or network interface 490.Network interface 490 enables computer 400 to communicate with remotedevices. For example, network interface 490 allows computer 400 tocommunicate over communication networks, such as LANs, WANs, theInternet, etc. Network interface 490 may interface with remote sites ornetworks via wired or wireless connections. Computer 400 receives dataand/or computer programs via network interface 490. Theelectrical/magnetic signals having contained therein data and/orcomputer programs received or transmitted by the computer 400 viainterface 490 also represent computer program product(s).

The invention can work with software, hardware, and operating systemimplementations other than those described herein. Any software,hardware, and operating system implementations suitable for performingthe functions described herein can be used.

As noted earlier, benefits of various embodiments of the currentinvention find applicability to the current 3GPP Release 7, to theupcoming Release 8, as well as to future releases of the 3GPPspecifications.

It is to be appreciated that the Detailed Description section, and notthe Summary and Abstract sections, is intended to be used to interpretthe claims. The Summary and Abstract sections may set forth one or morebut not all exemplary embodiments of the present invention ascontemplated by the inventor(s), and thus, are not intended to limit thepresent invention and the appended claims in any way.

The present invention has been described above with the aid offunctional building blocks illustrating the implementation of specifiedfunctions and relationships thereof. The boundaries of these functionalbuilding blocks have been arbitrarily defined herein for the convenienceof the description. Alternate boundaries can be defined so long as thespecified functions and relationships thereof are appropriatelyperformed.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the invention that others can, by applyingknowledge within the skill of the art, readily modify and/or adapt forvarious applications such specific embodiments, without undueexperimentation, without departing from the general concept of thepresent invention. Therefore, such adaptations and modifications areintended to be within the meaning and range of equivalents of thedisclosed embodiments, based on the teaching and guidance presentedherein. It is to be understood that the phraseology or terminologyherein is for the purpose of description and not of limitation, suchthat the terminology or phraseology of the present specification is tobe interpreted by the skilled artisan in light of the teachings andguidance.

CONCLUSION

Exemplary embodiments of the present invention have been presented. Theinvention is not limited to these examples. These examples are presentedherein for purposes of illustration, and not limitation. Alternatives(including equivalents, extensions, variations, deviations, etc., ofthose described herein) will be apparent to persons skilled in therelevant art(s) based on the teachings contained herein. Suchalternatives fall within the scope and spirit of the invention.

The breadth and scope of the present invention should not be limited byany of the above-described exemplary embodiments, but should be definedonly in accordance with the following claims and their equivalents.

1. A system, comprising: a policy control rules function (PCRF)Selection Function module housed in a non-Diameter Routing Agent (DRA)element within a home subscriber server (HSS), and adapted to deliverPCRF information to an operator's IP services via a Sh interface; and asecond PCRF Selection Function module housed in a 3GPP AAA server,wherein the PCRF Selection Function module and the second PCRF SelectionFunction module share a common state store.
 2. The system of claim 1,wherein the PCRF Selection Function module communicates PCRF informationto a serving gateway via a S6a interface.
 3. The system of claim 2,wherein PCRF information is communicated from the serving gateway to aPDN gateway via a S8 interface.
 4. The system of claim 2, wherein aBearer Binding and Event Reporting Function (BBERF) is deployed in theserving gateway.
 5. The system of claim 1, wherein the second PCRFSelection Function module communicates PCRF information to a PDN gatewayvia a S6b interface.
 6. A method, comprising: receiving a request forpolicy control rules function (PCRF) information by a PCRF SelectionFunction module housed in a non-Diameter Routing Agent (DRA) elementwithin a home subscriber server (HSS); and delivering the requested PCRFinformation to an operator's IP services via a Sh interface; wherein thereceiving uses a second PCRF Selection Function module housed in a 3GPPAAA server, and the second PCRF Selection Function module and the PCRFSelection Function module share a common state store.
 7. The method ofclaim 6, further comprising delivering of the requested PCRF informationto a serving gateway using a S6a interface.
 8. The method of claim 7,further comprising delivering of the requested PCRF information from theserving gateway to a PDN gateway using a S8 interface.
 9. The method ofclaim 7, wherein a Bearer Binding and Event Reporting Function (BBERF)is deployed in the serving gateway.
 10. The method of claim 6, whereindelivering of the requested PCRF information by the second PCRFSelection Function module to a PDN gateway uses a S6b interface.
 11. Anon-transitory computer-readable medium containing instructions forcontrolling at least one processor by a method, comprising: receiving arequest for policy control rules function (PCRF) information by a PCRFSelection Function module housed in a non-Diameter Routing Agent (DRA)within a home subscriber server (HSS) element; and delivering therequested PCRF information to an operator's IP services via a Shinterface; wherein the receiving uses a second PCRF Selection Functionmodule housed in a 3GPP AAA server, and the second PCRF SelectionFunction module and the PCRF Selection Function module share a commonstate store.
 12. The non-transitory computer-readable medium of claim11, wherein the method further comprises delivering of the requestedPCRF information to a serving gateway using a S6a interface.
 13. Thenon-transitory computer-readable medium of claim 12, wherein the methodfurther comprises delivering of the requested PCRF information from theserving gateway to a PDN gateway using a S8 interface.
 14. Thenon-transitory computer-readable medium of claim 12, wherein a BearerBinding and Event Reporting Function (BBERF) is deployed in the servinggateway.
 15. The non-transitory computer-readable medium of claim 11,wherein the delivering of the requested PCRF information by the secondPCRF Selection Function module to a PDN gateway uses a S6b interface.16. The system of claim 1, wherein the PCRF information includes theassigned PCRF identity.
 17. The method of claim 6, wherein the PCRFinformation includes the assigned PCRF identity.
 18. The non-transitorycomputer-readable medium of claim 11, wherein the PCRF informationincludes the assigned PCRF identity.
 19. A non-transitorycomputer-readable medium containing instructions for controlling atleast one processor by a method, comprising: receiving a request forpolicy control rules function (PCRF) information by a PCRF SelectionFunction module housed in a non-Diameter Routing Agent (DRA) elementwithin a home subscriber server (HSS); and delivering the requested PCRFinformation to a serving gateway via a S6a interface; wherein thereceiving uses a second PCRF Selection Function module housed in a 3GPPAAA server, and the second PCRF Selection Function module and the PCRFSelection Function module share a common state store.
 20. Thenon-transitory computer-readable medium of claim 19, wherein the PCRFinformation includes the assigned PCRF identity.